@maryamsulemani97: is the list of reserved words exhaustive? If so, does it have to be?

is the list of reserved words exhaustive? If so, does it have to be?

It isn't. We can document this somewhere else if needed

Ok, so after some actual testing I realised there's no "one size fits all" solution here. This is what we'll do:

• invalid_settings_ranking_rules: should include both _geoRadius and _geoBoundingBox. Using any of these words as custom ranking rules (e.g. _geoRadius:asc or _geo:desc) triggers an error
• invalid_search_sort: currently wrong. it says we can't use _geoPoint when not only we can do it, there's no other way of using _geoPoint. should include both _geoRadius and _geoBoundingBox
• invalid_search_filter: correct as it is. should not include _geoBoundingBox nor _geoRadius, as both of these are valid filter rules

bors merge

Build succeeded:

• check-builds (14)
• check-builds (16)
• check-links
• check-style
• vale